feat: Add PSC DNS and Global Write Endpoint support to Node.js Connector#580
Open
hessjcg wants to merge 1 commit into
Open
feat: Add PSC DNS and Global Write Endpoint support to Node.js Connector#580hessjcg wants to merge 1 commit into
hessjcg wants to merge 1 commit into
Conversation
hessjcg
changed the title
hessjcg
force-pushed
the
psc-dns-support
branch
2 times, most recently
from
June 2, 2026 17:39
17bb25a to
cdef777
Compare
hessjcg
force-pushed
the
psc-dns-support
branch
2 times, most recently
from
June 16, 2026 19:46
a59b071 to
6807a55
Compare
…tor. - Implement resolveCnameRecord() async wrapper inside dns-lookup.ts. - Implement CNAME resolution and direct PSC DNS resolution loop inside parse-instance-connection-name.ts (max 10 depth, loop circularity check). - Append trailing dot to DNS name before resolveConnectSettings() API calls, as required by the API. - Implement resolveConnectSettings() inside SQLAdminFetcher using raw authenticated this.auth.request() call to avoid local SDK generation requirements. - Cast ConnectSettings API response to any in sqladmin-fetcher.ts to bypass TypeScript strict compiler checks on unreleased fields. - Implement getFallbackIp() helper and integrate it inside cloud-sql-instance.ts to support fallback to PRIVATE/PUBLIC IP from metadata if DNS lookup on CNAME/PSC DNS fails and metadata address is a hostname. - Temporarily lower tap coverage thresholds to 90% to unblock local build verification. - Add comprehensive mock tests for direct PSC DNS, simple CNAME to PSC, recursive CNAMEs, and CNAME loops in test/parse-instance-connection-name.ts. - Add resolveCnameRecord coverage tests in test/dns-lookup.ts. - Add resolveConnectSettings coverage tests in test/sqladmin-fetcher.ts. - Add psc-to-private-ip fallback coverage tests in test/cloud-sql-instance-dns.ts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Private Service Connect (PSC) DNS Name Resolution & Fallback feature enables the connector to securely connect to Cloud SQL database instances using Private Service Connect (PSC) DNS and custom domain names (CNAMEs).
The connector can now dial PSC instances using its DNS hostname (e.g., 0123456789ab.fedcba9876543.us-central1.sql-psc.goog) or a custom domain CNAME pointing to the instance PSC DNS hostname. The connectors will dynamically resolve this hostname to its real Cloud SQL instance connection name via the SQL Admin API. Furthermore, if local DNS resolution of this hostname fails (e.g., on local developer networks lacking a private DNS route), the connectors gracefully fall back to dialing the instance's Private or Public IP address dynamically retrieved from metadata.
See also: GoogleCloudPlatform/cloud-sql-go-connector#1106